-
-
Notifications
You must be signed in to change notification settings - Fork 494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug fixes #280
Bug fixes #280
Conversation
Signed-off-by: NotAditya <[email protected]>
Signed-off-by: NotAditya <[email protected]>
Signed-off-by: NotAditya <[email protected]>
This fix doesn't contains #225 issues that would be fixed on the next pr this issue fixed #273 and also #276 and some more issues which weren't reported till now and i have seen people asking help in the support server so there's a lot of bug fixes this also includes this one you were asking about today in the support channel TypeError: Cannot read properties of null (reading 'Channel')
at module.exports (/home/pi/panaisv14/src/events/Lavalink/trackStart.js:38:22)
at processTicksAndRejections (node:internal/process/task_queues:96:5) Promise {
<rejected> TypeError: Cannot read properties of null (reading 'Channel')
at module.exports (/home/pi/panaisv14/src/events/Lavalink/trackStart.js:38:22)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
} |
I check all check be correct is there anything else added in the query where I can now accept it? |
Accept it |
I just saw but you made some changes on slashs command but not the message commands, an oversight? |
|
Is this from my commits? I didn't change the name field for the play command check my dev branch it doesn't includes similar names |
Well only made on play command and did on both other bugs were on emitters |
yes it comes from your clerk before setting it up I do checks and this concern did not exist before the addition of your commit |
But i don't find any conflicts in my part of the branch that has similar names? |
Can you try recloning my fork (dev branch) and try again |
it’s me I didn’t say anything on the other hand there is really a mistake |
So that issue was from your side right? |
Also 503? I want see a full screenshot |
yes |
there is nothing but that |
the function occurances has it i'll have to change it for all of them it seems you probably have a different setup for the bot anyways i'll do it and push again and then try |
@PandaIN95 you can retry now |
@NotAditya69 still same this bot is not destroying the player on right click disconnect in lavalink the player is getting paused |
how can that still be null what? can you send me the snippet here |
Desktop.2022.09.11.-.17.47.55.01.mp4Works perfectly |
it spam a lot so it’s som importance |
2022-09-11.18-33-42.mp4im not any errors in console now but still the same |
In next pr I'll fix them all this is also included in your #225 Since this isn't a serious issue I am gonna fix this in #225 this is totally random so this can appear on anything |
This seems to be a issue from your side since it works for me and Lukas too so i don't think that still stays a bug or so try to upgrade your node js and check |
@RafCodez if you don't mind can you check if the disconnect issue in #281 is fixed in my repo by using it |
@NotAditya69 im using node 16.17.0 |
Alright I'll try it later currently am not on my pc |
you guys can check now i have pushed the files once again check it, This time it should work i'll also share a video clip from my side Desktop.2022.09.12.-.12.47.26.01.mp4@RafCodez @PandaIN95 |
@NotAditya69 still the same For me |
how is it not working for you bruh, anyways player move will defo work but i want get new track data you see so either way i will have to reconnect again once disconnected or destroy the player else even if it's connected on the new play execution it won't play anything since erela.js doesn't resume sessions like shoukaku |
@PandaIN95 try now also make sure you have actually pulled the updates from my fork dev branch |
@NotAditya69 i fixed it revert all your changes you made for #281 |
but you only seem to destroy the player not resume the old queue? if that was the case should have told me |
@NotAditya69 bruhh i never said i want to resume the old queue i said on right click disconnect the player should destroy |
@LucasB25 you can merge this now if you have any other checking to do then feel free |
Description
Fixed many bugs in the main branch i'll list them here